Opened 13 years ago
Closed 12 years ago
#1838 closed defect (fixed)
error importing tiger/line data
Reported by: | jrossi | Owned by: | robe |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 2.0.2 |
Component: | tiger geocoder | Version: | 2.0.x |
Keywords: | history | Cc: |
Description
COMMIT NOTICE: INSERT INTO tiger_data.fl_tabblock(the_geom,intptlon,intptlat,awater,aland,funcstat,uace,ur,mtfcc,name,tabblock_id,blockce,tractce,countyfp,statefp) SELECT the_geom,intptlon10,intptlat10,awater10,aland10,funcstat10,uatyp10,uace10,ur10,mtfcc10,name10,tabblock_id,blockce10,tractce10,countyfp10,statefp10 FROM tiger_staging.fl_tabblock10; CONTEXT: SQL function "loader_load_staged_data" statement 1 ERROR: INSERT has more expressions than target columns LINE 1: …name10,tabblock_id,blockce10,tractce10,countyfp10,statefp10 …
QUERY: INSERT INTO tiger_data.fl_tabblock(the_geom,intptlon,intptlat,awater,aland,funcstat,uace,ur,mtfcc,name,tabblock_id,blockce,tractce,countyfp,statefp) SELECT the_geom,intptlon10,intptlat10,awater10,aland10,funcstat10,uatyp10,uace10,ur10,mtfcc10,name10,tabblock_id,blockce10,tractce10,countyfp10,statefp10 FROM tiger_staging.fl_tabblock10; CONTEXT: PL/pgSQL function "loader_load_staged_data" line 24 at EXECUTE statement SQL function "loader_load_staged_data" statement 1
Change History (7)
comment:1 by , 13 years ago
Milestone: | PostGIS 2.0.1 → PostGIS 2.0.2 |
---|
comment:5 by , 12 years ago
Add to this fails for California since name field is evidentally not long enough
see post: http://www.postgis.org/pipermail/postgis-users/2012-August/035052.html http://www.postgis.org/pipermail/postgis-users/2012-August/035051.html
Need to make changes
{{{ —making name bigger than it needs to be just in case
ALTER TABLE tiger.tabblock ALTER COLUMN name TYPE varychar(20);
ALTER TABLE tiger.tabblock ALTER COLUMN tabblock_id TYPE varchar(16);
}}}
comment:6 by , 12 years ago
fixed at r10179 for 2.1.0 (tiger_2011) still need to backport changes to 2.0
comment:7 by , 12 years ago
Keywords: | history added |
---|---|
Resolution: | → fixed |
Status: | new → closed |
fixed for 2.0 at r10716
Still haven't had a chance to look at this. I may just dismiss it since the reporter didn't have issue using tiger 2011 routines.